[meta] CSS.enable
Categories
(Remote Protocol :: Agent, task)
Tracking
(Not tracked)
People
(Reporter: automatedtester, Unassigned)
References
()
Details
(Keywords: meta, Whiteboard: [method=CSS.enable])
A real world use of puppeteer is to extract CSS from the page. in https://github.com/bartveneman/extract-css-core they use the CSS.enable command
|
||
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
(In reply to David Burns :automatedtester from comment #0)
A real world use of puppeteer is to extract CSS from the page. in https://github.com/bartveneman/extract-css-core they use the CSS.enable command
Note that this also covers CSS.disable, DOM.enable, DOM.disable, CSS.startRuleUsageTracking, as well as CSS.stopRuleUsageTracking. I don’t think we have bugs for all of those.
|
|
||
Comment 2•5 years ago
|
||
Useful background material is CSSCoverage in Puppeteer: https://github.com/puppeteer/puppeteer/blob/62da2366c65b335751896afbb0206f23c61436f1/lib/Coverage.js#L182
|
|
||
Comment 3•5 years ago
|
||
We have for DOM.enable and DOM.disable.
|
|
||
Comment 4•5 years ago
|
||
I forgot to check earlier, but spotted that the DOM domain has in the excess of a dozen events associated with DOM.enable/DOM.disable. Most tied to mutation observers in some way. Didn’t check which are used by extract-css-core.
|
||
Comment 5•4 years ago
|
||
The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months.
:whimboo, maybe it's time to close this bug?
|
|
||
Comment 6•4 years ago
|
||
Closing as inactive for given that we don't have free resources to get this implemented for now.
Description
•